I modified the raw_records (DAQReader) plugin to allow for creating raw_records_ext, a new type of data that is intended to be used for measuring signals out of the TPC. For example, we can use it as a "software external trigger": measure some signals with an external TPC and select on events that come in coincidence with some peak in the external PMT.

For this reason, we want to have a complete separate chain of raw_records-peaks that follow a separate processing wrt the TPC PMTs. This is implemented in a very similar way as the neutron and muon veto detectors are treated in XENONnT.

We define the PMT channels in the context channel map:

channel_map={
            'bottom': (0, 0), 
            'top': (1,4), 
            'external': (5,10)
 }

'top' and 'bottom' are required, while 'external' defaults to (-1,-1).

We now have:

• raw_records_ext
• records_ext
• peaks_ext
• peak_basics_ext

These copies of the original plugins do all similar things but just with raw_records coming from external channels (in this case channel 5). Some fine tuning might be needed on the specific requirements for the processing of these peaks. The processing of normal records and peaks should be unchanged.

NOTE: it is important to preserve always the same lineage_hash for raw_records. This is possible by having the raw_records as the last type produced in the DAQReader plugin, because the lineage comes from the last plugin.

Here an example notebook used to test this new framework, assuming that channel 4 would be an external PMT.

new_raw_records.pdf